Trigger without dxl?

Hi,

I've been asked to analyze the triggers that exist in our DOORS projects/modules. (We've lost the history of where they came from and why.) I'm having trouble figuring out what one of the triggers does.

Trigger: B:specific close for Update FTS Attributes 1231
Level: module
Type: post
Event: close
Attribute:
Kind: builtin
Scope: FTS
Dxl:

The trigger exists in many different modules, and the number at the end of the trigger name is different for each one. There is no DXL code stored in the trigger, so I can't tell what it does. I've looked at some of the other trigger attributes as well, but didn't find anything useful there. I'd appreciate any suggestions you can provide on what this trigger does or how to find out.

Regards,
wendy
wendy64ca - Wed Feb 24 10:55:36 EST 2010

Re: Trigger without dxl?
johnzweck - Wed Feb 24 11:53:34 EST 2010

These triggers seem to be attached to the trigger with the name between "specific close for" and the number at the end. If the original trigger is deleted, this one goes with it.

Re: Trigger without dxl?
wendy64ca - Wed Feb 24 12:13:47 EST 2010

johnzweck - Wed Feb 24 11:53:34 EST 2010
These triggers seem to be attached to the trigger with the name between "specific close for" and the number at the end. If the original trigger is deleted, this one goes with it.

Wow - how did you know that? I looked through the documentation and couldn't find anything helpful.

There is also a trigger called "Update FTS Attributes", but I hadn't noticed the correlation in the names. Do you think this one does something additional to what that one does, or not?

wendy

Re: Trigger without dxl?
Mathias Mamsch - Wed Feb 24 14:05:22 EST 2010

wendy64ca - Wed Feb 24 12:13:47 EST 2010
Wow - how did you know that? I looked through the documentation and couldn't find anything helpful.

There is also a trigger called "Update FTS Attributes", but I hadn't noticed the correlation in the names. Do you think this one does something additional to what that one does, or not?

wendy

I am not completly sure, but I think if you install a dynamic trigger there is always a "Specific XY" trigger that comes with it. Is the Update FTS Attributes Trigger installed dynamically by another script?

Regards, Mathias

Re: Trigger without dxl?
wendy64ca - Thu Feb 25 08:20:45 EST 2010

Mathias Mamsch - Wed Feb 24 14:05:22 EST 2010
I am not completly sure, but I think if you install a dynamic trigger there is always a "Specific XY" trigger that comes with it. Is the Update FTS Attributes Trigger installed dynamically by another script?

Regards, Mathias

Hi Mathias,

I don't know - how could I tell?

wendy

Re: Trigger without dxl?
doors36677 - Thu Feb 25 08:29:58 EST 2010

wendy64ca - Thu Feb 25 08:20:45 EST 2010
Hi Mathias,

I don't know - how could I tell?

wendy

Find the source of the original trigger and install in a test module.

Re: Trigger without dxl?
jsarkic - Thu Feb 25 09:35:54 EST 2010

If you get a handle to the trigger and print it using "print dxl(trigger)" and you do not see any code, then your trigger is not doing anything. This trigger can be removed.

Re: Trigger without dxl?
Mathias Mamsch - Thu Feb 25 10:09:09 EST 2010

wendy64ca - Thu Feb 25 08:20:45 EST 2010
Hi Mathias,

I don't know - how could I tell?

wendy

My fault, it cannot be a dynamic trigger since it has a name ... So just dont worry about the "specific xy" triggers, they are just doors internal stuff. Regards, Mathias

Re: Trigger without dxl?
roybond - Thu Feb 25 13:17:03 EST 2010

There is a tool which was developed by Michael Sutherland, called 'Delete Persistent Triggers' which may be of some use to you. As its name implies, you can use it to delete Triggers from your Module/Project, but it will also provide you with the all details of the Trigger as it is defined.

The tool can be downloaded from http://galactic-solutions.com

Roy.

Re: Trigger without dxl?
llandale - Thu Feb 25 16:55:07 EST 2010

jsarkic - Thu Feb 25 09:35:54 EST 2010
If you get a handle to the trigger and print it using "print dxl(trigger)" and you do not see any code, then your trigger is not doing anything. This trigger can be removed.

No. As the manual says you only see the dxl(trg) for Persistent triggers. You don't see the dxl for Dynamic nor built-in. Look at the "king(trg)" with values of: dynamic, stored or builtin.

for Trigger in whatever loops should bypass dynamic and builtin triggers. Never tried, but I don't think you can delete builtin triggers.

The Builtin triggers are a mechanism for cancelling the other trigger. If the persistent trigger is stored in a module and displays a dialog, the Builtin trigger will cancel the dialog when the module closes, as evedenced by the fact that these Builtin triggers in modules are post-module-close triggers.

  • Louie

Re: Trigger without dxl?
jsarkic - Fri Feb 26 11:38:33 EST 2010

llandale - Thu Feb 25 16:55:07 EST 2010
No. As the manual says you only see the dxl(trg) for Persistent triggers. You don't see the dxl for Dynamic nor built-in. Look at the "king(trg)" with values of: dynamic, stored or builtin.

for Trigger in whatever loops should bypass dynamic and builtin triggers. Never tried, but I don't think you can delete builtin triggers.

The Builtin triggers are a mechanism for cancelling the other trigger. If the persistent trigger is stored in a module and displays a dialog, the Builtin trigger will cancel the dialog when the module closes, as evedenced by the fact that these Builtin triggers in modules are post-module-close triggers.

  • Louie

I agree that you cannot get access to built-in triggers. Persistent trigger code is easy to get access to using dxl(trg) - I apologize if my previous reply was misleading. As to dynamic triggers, my understanding is that these triggers only exist within the context of your executing DXL code that instantiated the triggers. When your code terminates, so does your dynamic trigger. The only triggers you should be able to get access to are persistent triggers.

Re: Trigger without dxl?
llandale - Fri Feb 26 12:56:52 EST 2010

jsarkic - Fri Feb 26 11:38:33 EST 2010
I agree that you cannot get access to built-in triggers. Persistent trigger code is easy to get access to using dxl(trg) - I apologize if my previous reply was misleading. As to dynamic triggers, my understanding is that these triggers only exist within the context of your executing DXL code that instantiated the triggers. When your code terminates, so does your dynamic trigger. The only triggers you should be able to get access to are persistent triggers.

I think you should be able to see the code for Dynamic triggers; heck I want to see exactly what its doing.

Re: Trigger without dxl?
wendy64ca - Fri Feb 26 13:34:04 EST 2010

llandale - Thu Feb 25 16:55:07 EST 2010
No. As the manual says you only see the dxl(trg) for Persistent triggers. You don't see the dxl for Dynamic nor built-in. Look at the "king(trg)" with values of: dynamic, stored or builtin.

for Trigger in whatever loops should bypass dynamic and builtin triggers. Never tried, but I don't think you can delete builtin triggers.

The Builtin triggers are a mechanism for cancelling the other trigger. If the persistent trigger is stored in a module and displays a dialog, the Builtin trigger will cancel the dialog when the module closes, as evedenced by the fact that these Builtin triggers in modules are post-module-close triggers.

  • Louie

Thanks all, I think I've got what I need. I confirmed that if I delete the "Update FTS Attributes" trigger, the builtin trigger also disappears, and when I recreate the "Update FTS Attributes" trigger, the other one comes back as well.

The builtin trigger is shown when I do a "for trigger in module" loop, and I can delete it (at least, I don't get an error when I try - I didn't actually try deleting it without also deleting the "Update FTS Attributes" trigger).

Thanks again.
wendy